1.1. Typographical Conventions

This document uses the following typographical conventions:

• Fixed-width bold text indicates commands and command options in syntax definitions, examples, and running text.

• Italicized text indicates user-supplied values. For example, -deviceid device_ID indicates that you supply a device ID for device_ID after the -deviceid parameter. Italics also indicate emphasis and the titles of books.

• Bold text indicates GUI elements (including menus, menu items, labels, buttons, icons, and folders), keys on the keyboard (for example, Enter and ESC), and literal values.

• Fixed-width text indicates screen output.

• The backslash character ( \ ) is used to indicate a line break in a command. When issuing a command, you do not need to enter this symbol.

• Lists from which you must choose an item in syntax descriptions are enclosed in braces ( { } ). For example, {true | false} indicates that you must choose between true and false. Do not enter the braces in the command.

• The vertical column ( | ) separates items in a list of choices enclosed in braces in syntax descriptions, as shown in the preceding example.

• Ellipses ( ... ) in syntax descriptions indicate that you can repeat the preceding item one or more times. Ellipses in examples indicate that the information was omitted for the sake of brevity.

• An item in syntax descriptions enclosed in square brackets ( [ ] ) is optional. For example in the following command, the [ ] characters indicate that the -nodetype parameter is optional:

  spinserver::> spinaccess cifs servers new -vsname VS1 -netbios NB1 -domain ENG [-nodetype H]
  

  Leaving the optional parameters out of the command line has no consequences for command execution. Do not enter the brackets as part of the command.

• In command examples, the CLI prompt is represented as follows:

  spinserver::>
  

  On a SpinServer system, the word spinserver in the prompt is replaced with the name of the SpinServer itself. For instance, on a SpinServer named Server1, the CLI prompt is the following:

  Server1::>
  

1.2. Organization of the Guide

This guide provides you with information and examples for the specific tasks that you must perform to configure and maintain the SpinServer system. The document is divided into the following parts:

• Part Part I in SpinFS 2.5 Administration Guide lists the prerequisites needed for SpinServer administration and introduces the administrative interfaces.

• Part Part II in SpinFS 2.5 Administration Guide provides instructions for installing the SpinFS software on a SpinServer and creating a basic configuration.

• Part Part III in SpinFS 2.5 Administration Guide discusses concepts and tasks for managing data on a SpinServer system.

• Part Part IV in SpinFS 2.5 Administration Guide discusses concepts and tasks for managing a SpinServer system.

• Part Part V in SpinFS 2.5 Administration Guide provides information on working with system messages.

1.3. SpinServer Documentation

The following documentation is provided for the SpinServer:

• SpinFS Architecture Basic Concepts Guide

• SpinFS 2.5 Administration Guide

• SpinFS 2.5 Administration Reference

• SpinFS 2.5 Messages and Troubleshooting Guide

• SpinFS Release Notes

• SpinServer 4100 Installation Guide

• SpinServer 4100 Quick Start Guide

• SpinServer Supported Storage Release Notes

• SpinServer Site Preparation Guide

Documentation is available in PDF format and can be accessed from the SpinServer browser management interface or from the CD. To access the documentation from the CD, open the root_directory/SpinDocs/index.html file in a web browser, where root_directory is the root directory of the CD.